what is a configuration and what is a rule?

I have defined this on line 46:

Service faults can be configured using the endpoint at /_localstack/chaos/faults.
The configuration schema consists of an array of one or more rules, where each rule specifies the conditions for the fault to occur.
When active, rules are evaluated sequentially on every request to LocalStack until the first match.

Is it unclear?

ah, now I see that the payload accepts an array. so this array would be the configuration and each element a rule?

that would mean that a configuration is identified by an id, and GET ./chaos/faults would return the configs with their ids? To update a configuration I'd then PATCH ./chaos/faults/<configuration_id>

similarly for the rules there is a DELETE so I'd assume they are also identified by an id DELETE ./chaos/faults/<fault_id>/<rule_id>

but maybe I'm thinking to complicated here... 🤔 having all that auto generated with make things much easier :D

There is just one configuration. Multiple configurations are not supported.

ok, then I guess just needs to be updated

GET: Get current configuration
POST: Add new configuration
PATCH: Add a rule
DELETE: Delete a rule

maybe a GET and PUT is sufficient here then. instead of the term 'configuration' just 'list of rules' might be easier to understand.